*I

PipBase InfoéPipBase HelpµBasic Configurations
Advanced Configuration└Everyday Usei Casual use▓"PipBase Authors"%PipBase Support BBS&'Acknowledgements!)Help on help+Pip Reply and VolvoxReplyV,What is PipBase?ù3What does "PIP" mean?╕?Interactive useHAWhat About Registering?AC/25"G/NOEMS▄HdADDROUTE├IeAREAFIX╧MfBOOSTUSgBTCHANGEΘUhBTPOLL`WiBTREQUESTWXjBTSENDùYk  ƒ
[lCREATE∞\mDELETEjcnDELROUTEµdoDESTROYfpEXPORT╫fqGHOST]irHELPcksINDEX╗mtIMPORTΩpuINFOnrvLINKUswLISTAKASÆtxLISTAREA╨uyLISTAREASçvzLISTCFGNw{LISTEXPORTx|LISTFRIENDS.y}LISTORIGINSöy~LISTROUTE·yLISTUSERSmzÇLOCK&{éMARKy|âMOVEAREA}äPACKö}àPICKORIGIN├åPOST·üçPURGE┌îêREADƒÅëREADAREAnæèRESET5DMSGIDêôïRESETELIM4DöîRESETREPLYiöìRESETEXPORT-òÄRESETROBOTlûÅRRùÉSCANXⁿÿæSETÜÆSET5DMSGIDΘ£ôSETAREAAKAG₧öSETAREAFIX┴ƒòSETAREALEVEL^íûSETAREANAMEºóùSETAREANOTESAúÿSETATTACHES
ñÖSETELIM4DÄ¿ÜSETEXPORT┴½¢SETFAKE╬¡£SETFRIEND╠▒¥SETGHOST²╢₧SETINBOUND░╕ƒSETLASTREAD╛║áSETLOGFILE█╗íSETLOGLEVEL╣╝óSETLOGTYPEΘ╜úSETNODE>┐ñSETORIGIN┬ÑSETOUTBOUND┐┼ªSETPACKER'╟ºSETPACKERDIR╒╚¿SETPIPDIRO╩⌐SETPURGE╠¬SETREPLYF═½SETROBOT≡═¼SETRR╗╨¡SETTAGq╥«SETTEAR≤╙»SETTEMPDIRj╓░SETUNPACKERs╪▒SETUSERR┌▓SETUUCPX▄│SHOWLASTREAD┼▐┤STATú▀╡UNDELETE╝α╢UNLOCKÑß╖UNMARKYΓ╕SORT╒Γ╚REPLYºΣ╔Basic Pip Reply Topicsùτ▄Pip Reply area selection╟Φ▌Shell to operating system╛Ω▐Pip Reply message list░δ▀Pip Reply change messageòεαFlags@±ßPip Reply main screen≈ΓInternal text editorπJOLLY`ΣROT-13┼σRegistered Users Only OptCσCarbon-Copy┌µchange originKτuudecode\ΦCC: disabled1·Yes or not?╗,Pip General MenuO-Program\AboutΦ.Program\Shell┤/Program\ExitL0Program\Terminal≈1Program\Poll Boss4|Binkley Termá}Fossil Driver~ÅAbout ScreenèÉPip Mail Menu'æMail\Reply½ÆMail\ImportzôMail\Export∞öMail\Linkô!òMail\Purge°"ûMail\Pack $ùMail\Return Receiptú%ÿMail\Ghost Writer▐&ÖMail\Rebuild Indexes╞'ÜMail\Statistics«(¢Mail\SortQ)⌠Pip Setup Menu*⌡Setup\General,÷Setup\Directories╗>≈Setup\Message Areas⌡B°Setup\Origins╪M∙Setup\Network AddressesEO·Setup\FriendsóP√Setup\Routing,XⁿSetup\UUCP Gateway├^²Setup\Usersä_■Setup\Robotsa Setup\Log FileBdSetup\Editor Preferences!fSetup\QuotesfoSetup\ColorsutSetup\Viewer▀u&External Viewerºä'userlistCë(alias listφô)nodelist/pointlist compil7û*BuildListÿXPip Menu Help╬ÿXPip Menu Help    
PipBase Help File
Compile with TCXL

*B 10,PipBase Info
This GREAT new messagebase format was invented in Italy,
in 1990/'91, by Roberto Piola and Elio Fenoglio.

The source code for basic Pipbase management procedures
is in P.D., as well as the documentation about the format.
It's distributed as MessageObject, in C++ source code.
Look for files named MSGOBJ*.*.

For more info, please contact the authors.

^Help on help^ (point and press Enter to get it)
^PipBase Authors^             ^PipBase Support BBS^
^Acknowledgements^            ^PipBase Help^
^Pip Reply and VolvoxReply^   ^What is PipBase?^
^What does "PIP" mean?^
*E
*B 11,PipBase Help
PIP is a collection of basic procedures to manage PIPBase
messages, made by Roberto Piola - Italy - 1991/93
see also: ^PipBase Info^         SUPPORT PIPBASE PROJECT!

Syntax of a PipBase call from command line is:
   PIP <command> [parameters...] [^/25^] [^/NOEMS^]
Select the set of commands (or the switch) you are
interested to:

^Basic Configuration^ (command-line)
^Advanced Configuration^ (command-line)
^Everyday Use^ (command-line)
^Casual use^ (command-line)
^Interactive use^ (windowed interface)
^Help on help^ (point with cursors and press Enter
                to get it, or click with mouse)
*E
*B 12,Basic Configuration
^BOOST^ key
^CREATE^ area# "description" tagname|#LOCAL|#NETMAIL|#BAD|
                            #DUPES message# day# [origin#]
^DESTROY^ area#
^LISTAKAS^
^LISTAREAS^ [VERBOSE]
^LISTCFG^
^LISTEXPORT^
^LISTFRIENDS^
^LISTORIGINS^
^LISTROUTE^
^LISTUSERS^
^SET^ pipbase_directory logfile_name TINY|SMALL|MEDIUM|
                                      LARGE|EXTRA-LARGE
^SETATTACHES^ netmail_*.msg_directory PIP!|FRODO|D'B|
          BINK|TRAPDOOR [PACK-MATRIX|DYNAMIC-PACKING]
^SETEXPORT^ area# friend#
^SETFAKE^ fakenet#
*P
^SETFRIEND^ friend# zone# net# node# point# packer
                               "packer_parameters"
^SETINBOUND^ inbound_directory
^SETLOGFILE^ filename
^SETLOGLEVEL^ 0|1|2|3
^SETLOGTYPE^ BT|FD
^SETNODE^ aka#|0 zone# net# node# point# domain
^SETORIGIN^ origin# "origin text"
^SETOUTBOUND^ outbound_directory
^SETPACKER^ packer_program.ext "parameters"
^SETPACKERDIR^ packer_directory
^SETPIPDIR^ pipbase_directory
^SETPURGE^ area# messages# days#
^SETTEMPDIR^ temporary_directory
^SETUSER^ user# "user name"
*E
*B 13,Advanced Configuration
^ADDROUTE^ friend# ALL|ZONE|NET|NODE|HUB|POINT
               [zone# [net# [node# [point#]]]]
^DELROUTE^ rule#
^RESETELIM4D^
^RESETREPLY^
^RESETEXPORT^ area# friend#
^RESETROBOT^ KILLREQUESTS|KILLANSWERS
^SETAREAAKA^ area# level#
^SETAREALEVEL^ area# level#
^SETAREANAME^ area# "description"
^SETAREANOTES^ area# "notes"
^SETAREAFIX^ friend# password level#
^SETELIM4D^
^SETGHOST^ "Ghostwriter's name"
^SETREPLY^
^SETROBOT^ KILLREQUESTS|KILLANSWERS
^SETRR^ return_receipt_file
*P
^SETTAG^ area# tag
^SETTEAR^ "your tearline"
^SETUNPACKER^ jolly_unpacker_program_name "parameters"
^SETUUCP^ outbound_zone net node inbound_zone net node
*E
*B 14,Everyday Use
^AREAFIX^
^DELETE^ area# message#
^EXPORT^
^GHOST^
^IMPORT^
^INDEX^ [area#]
^LINK^ [area#]
^LISTAREA^ area# [NEW]
^LOCK^ area# message#
^MARK^ area# message#
^PACK^ [area#]
^PICKORIGIN^ area# origin#
^POST^ area# filename.ext "from..."|user# "to..."|user#
                "subject" [zone net node point [PRIVATE
                [HOLD|CRASH] [ATTACH|REQUEST] [KILL]
                [RR] [AUDIT]]
*P
^PURGE^ [area#]
^READ^ area# message# [MARK]
^READAREA^ area# [NEW] [MARK]
^REPLY^
^RR^
^SCANX^ user# [area#]
^SORT^ [area#]
^STAT^ [user#]
*E
*B 15,Casual use
^BTCHANGE^ zone net node point [CRASH|HOLD|NORMAL]
^BTPOLL^ zone net node point [CRASH|NORMAL]
^BTREQUEST^ zone net node point filename.ext
                              [CRASH|NORMAL]
^BTSEND^ zone net node point \path\filename.ext
                              [CRASH|HOLD|NORMAL]
^BTUPDATE^ zone net node point \path\filename.ext
                              [CRASH|HOLD|NORMAL]
^HELP^ [specific_command]
^INFO^
^MOVEAREA^ oldarea# newarea#
^SETLASTREAD^ user# area# message#
^SHOWLASTREAD^ user# area#
^UNDELETE^ area# message#
^UNLOCK^ area# message#
^UNMARK^ area# message#
*E
*B 16,PipBase Authors
Roberto Piola                              Elio Fenoglio
via D.Godino, 8/C                 v.Brigata Cagliari, 27
10060 S.Secondo di Pinerolo (TO)     10060 Pinerolo (TO)
ITALY                                              ITALY
tel.:+39-121-500663                  tel.:+39-121-396548
fidonet: 2:334/108.57 or 2:334/306.666
internet: roberto@p666.f306.n334.z2.fidonet.org
      or: roberto@p57.f108.n334.z2.fidonet.org
UUCP:...!gear!wolf!334!306.666!roberto

^PipBase Info^
*E
*B 17,PipBase Support BBS

               Oficial Support BBSes are

                     Lord Drake BBS
                     +39-11-7724247
                 fidonet node 2:334/400
Sysop: Fabrizio Croce (he was the sysop of the first BBS
I called... the BBS has changed, but the sysop is always
our beloved sysop).

                      WinFront BBS
                     +39-11-5681765
                 fidonet node 2:334/108
        Sysops: Marco Russo & Corrado Molinatto
^PipBase Info^
*E
*B 18,Acknowledgements
Thanks to Silvan Calarco, fidonet 2:334/100.2 for mailer 
procedures, to Elio Fenoglio, fidonet 2:334/306.4, for 
initial ideas, debugging, sort procedure, and much other, 
to Valerio Leomporra (fidonet 2:335/311.48) and Michele 
Pianta' (fidonet 2:334/108.17) for ROT-13 algorithm, to 
Thomas Wagner for his swapping procedure and to all my Beta 
testers, especially Paolo Rosa, Hal, Mac and Murdock.

 Support PipBase!

^PipBase Support BBS^
^PipBase Info^
*E
*B 19,Help on help
To navigate between help pages: point the reference with
the mouse and click, or highlight the desired topic with
cursor keys and then press Enter.
To browse pages: use PgUp and PgDn keys.
To back-up, press Alt-F1.
To leave help, use the ESCape key

^PipBase Info^
^PipBase Help^
*E
*B 20,Pip Reply and VolvoxReply
PipReply and VolvoxReply, a little Volvox history.

"...AND DON'T ASK WHAT DAMN IS A VOLVOX".

In one of the best italian echomail areas, Dewdney.Ita, a
lot of Volvox was waiting for a Volvox editor, an editor
that automatically recognize if the sender of the message
we are replying to is a Volvox or an antivolvox (lower
case is a way to make them worse and less important), and
in base of this fact select the appropriate quote string.

Another necessary thing was the quote margin, measured on
the quoted text sender. An example, to distinguish
Piermaria Maraziti from Paolo Marincola, we wanted to
quote the former as PmM> and the latter as PMA> (or _pma_,
that is more similar to his signature).
*P
I was working at the PipBase project, and so I started
also with a little VolvoxReply, added to PipBase.

But another Volvox, Marco Mariani (usually quoted as .\\ >
because his signature is .\\arco) beated me on the time
and when I asked for someone interested in the porting
from MSDOS to Amiga of VolvoxReply, he said: "Ah no! I
already finished VolvoxReply for Amiga. Doing the porting
from Amiga to IBM is your work".

Since there wasn't something like Arexx in my messydos
hard disk, I preferred to rewrite my editor (well,
expanding it and adding lots of options to the original
project), renaming it PipReply. So, antivolvox too can use
it (and pay me the registration!).
*P
Clear? No? Please matrix me, or join the Volvox community
in Italy.

Important notice: Volvox is a (c) Volvox; antivolvox is a
)c( [read it "copyleft"] antivolvox.

Eventually, you may contact Stefano Costa, fidonet
2:332/210 to have a motorsaw-attach of what is a Volvox
(notice that he too is a Volvox), or you may request the
VOLVOX42.* file from some italian Volvox BBSs (if you
read Italian).
*E
*B 21,What is PipBase?
What is PipBase?

PipBase is a new -COMPRESSED- message base, developed by
Roberto Piola (2:334/306.666@fidonet.org) and Elio
Fenoglio (2:334/306.4@fidonet.org) in 1991.

In projecting PipBase, we had these targets:
a) It will have to save space: messages will be stored in
   a compressed format and without slack.
b) It will be fast: we had to have a compromise between
   speed and space gain (yes, we could use ARJ algorithm
   to compress messages and to save another 20-30% more
   than actual gain, but who can wait some seconds in
   passing from a message to another?): a not very good
   compression rate can be a good idea, if doing so you'll
   be faster than QuickBase.
*P
c) It will not have that heavvy limits of QuickBase: more
   than 200 areas, more than 16 Megabytes in the message
   base! PipBase can handle up to 32768 messages areas,
   containing up to 32768 messages each, to fill up to 2
   GigaBytes of disk space (compressed! i.e.: you'll have
   effectively MORE than 2 GB of text displayed to your
   users) with your messages.
Elio suggested ideas a and c; I (Roberto) developed
algorithms meeting point (b) (to reach my target, I
developed them in interpreted BASIC on my Z88, a Z80-based
computer... and they were quick enough).

Marco Maccaferri soon implemented Pip message base in his
Lora CBIS, good work! while I was developing PipBase, the
mail processor and the message base utilities, and
PipReply, a full screen editor, ideal for points.
*P
After a while, I melted both PipBase and PipReply in an
unique Pip* executable file, and I rewrote the message
base API (in C++)

Pip* offers these functions:
- netmail and echomail importing/exporting and forwarding
- it operates both in a Front Door/D'Bridge or in a
  Binkley Term/Lora environment, with full 4-Dimensional
  support
- areafix and ghostwriter facilities
- options to read messages, and to send as message any
  text file
- a purger to delete old messages, and a packer to
  eliminate them from disk
- a message scanner to find messages for a user
- options to recover a damaged message base
- mouse operated
*P
- special personalized quotes... you'll love them!
- all packers are supported: ARC,PAK,ZIP,ZOO,LHARC,ARJ,SQZ
  and LHA are automatically distinguished; if a new packer
  will appear, a special "Jolly unpacker" option can be
  used to add this new packer; no problem for compression:
  you may use almost everything (all described packers,
  with any kind of parameters, plus ARCHI and everything
  that will be created in future).
- an external editor is used: you'll not have to learn new
  commands, but you'll continue to use your favourite text
  editor to write messages
- it handles transparently UUCP gateways: if you want to
  send a message in internet, simply write the internet
  address in the "Addess" field, or place it in the
  extended userlist
*P
For PipBase there are also interesting utilities, the
Robot Engine and the 4D/UUCP forwarder... but it is
another story...
*E
*B 22,What does "PIP" mean?
What does PIP mean? :-)

Lots of peoples are losing their sleep in guessing that!
Try and matrix your explanation of this TLA to Roberto
Piola, 2:334/108.57@fidonet.org... you'll win a surprise,
when you'll guess it!

The most fantasious interpretation was made by Werner
Berghofer (2:310/2.0): PIP is a remind from CP/M's
Peripheal Interchange Program... Wrong!
*E
*B 23,Interactive use
Pip* has both a command-line interface (see ^PipBase Help^
screen), ideal for batch operations, and a more
user-friendly interactive interface, with windows and
pull-down menus.

The windowed interface is entered when you issue the PIP
command without parameters form the DOS prompt.

Use mouse to select all functions.

See help screens for each submenu:
^Pip General Menu^
^Pip Mail Menu^
^Pip Setup Menu^


See also ^PipBase Info^ and ^PipBase Help^
*E
*B 24,What About Registering?
Pip* is a Shareware product; it means that the authors
leave you all the freedom to test the program without
paying a cent, but you must pay if you want to use them
regularly.

Authors spent a lot of time (days stolen to study and
nights stolen to sleep) in developing them; paying a
little amount is the best way to say "thanks".

If you want to register, you'll receive a key that will
enable some advanced features of PipBase: Areafix,
GhostWriter... and so on, and it will eliminate those
annoying beeps and pauses at the start and at the end of
Pip*

<Press PgDn> to know how to register
*P
The registration costs 45000 Italian Liras.

If you're already a registered user of PipBase or
PipReply, the new upgrade key will cost you only 7000
Italian Liras, or something like a drink in a pub if you
visit my city.

Send money in italian currency, using a mail cheque, to:
Roberto Piola, via D.Godino 8/C, 10060 S.Secondo di
Pinerolo (TO) - ITALY

*E
*B 25,/25
The /25 switch

Usually, when you invoke Pip ^REPLY^ message editor or PIP
interactive interface (see ^Interactive use^), Pip sets
the video mode accordingly with the values set in the
^Setup\Viewer^ screen.

If you don't want to enter the 43/50 lines mode, you may
add a "/25" on the command line.

Important: the /25 switch is MANDATORY if you want to use
Pip* under Microsoft Windows 3.1 with a standard VGA.
*E
*B 26,/NOEMS
The /NOEMS switch

If you've EMS memory installed, but you don't wuant Pip*
using it, specify a /NOEMS switch on the command line.

It's reccomended to do this when running Pip* under
Microsoft Windows.
*E
*B 100,ADDROUTE
PIP ADDROUTE friend# ALL
PIP ADDROUTE friend# ZONE zone#
PIP ADDROUTE friend# NET zone# net#
PIP ADDROUTE friend# HUB zone# net# hub#
PIP ADDROUTE friend# NODE zone# net# node#
PIP ADDROUTE friend# POINT zone# net# node# point#

Each of these commands defines a routing rule for packed
matrix messages. Routing means that all messages for a
group of nodes will be packed togheter and sent to a
single node ("host" or "hub").

All target nodes have to be defined with ^SETFRIEND^ (see)
before you route something via them. Each commands tells
to the system to route the specified point, node (or the
cluster of the node and all his points), hub, net or zone
via the specified "target" friend.
*P
You may see the routing rule list with ^LISTROUTE^ (see)
and remove routing rules with ^DELROUTE^ (see).

Points wanting to route all their mail via their boss
(that is the most natural thing, and points not following
this rule are very rare) don't need a ROUTE boss_friend#
ALL: it's a default.
*E
*B 101,AREAFIX
PIP AREAFIX

This is the first Robot inserted in PipBase.

Its function is simple: when a point or another BBS wants
to be linked to a conference (see ^SETEXPORT^), the sysop
has to write a #NETMAIL message to the user called
"Areafix" on the conference feeder (the boss, if you're a
point), containing as subject your areafix password
(contact the feeder sysop for obtaining it), and in the
text the tag names of the conferences you desire.

When you're bored of an echomail area, you may unlink it
simply by addressing a message to Areafix and specifying
the tag names of the conferences you don't want any more,
preceeded by a minus. By example: if you want to detach
yourself from the conference CHATTER.ITA, you'll have to
specify -CHATTER.ITA in the text of the message.
*P
If you place a -Q in the subject of the message (after the
password, of course), you'll receive the listing of all
conferences you're linked to; if you place a -L (the case
doesn't matter), you'll receive the list of all
conferences supported by your feeder; if you put a -H,
you'll receive a complete help on how to use AreaFix.

Notice: areas with an areafix level greater than your are
not listed with a -L.

When the feeder runs PIP AREAFIX, the Area Robot scans all
netmail messages and answers them.

Important: to have this function, your boss has to
register (see ^BOOST^)!
*E
*B 102,BOOST
PIP BOOST key|NULL

When your registration key arrives in the form of an
intricate sequence of letters and digits, type PIP BOOST
"that-sequence", to place the key into PipBase. It will
open a lot of new possibilities!
To obtain the key, please read allegated docs and/or
contact the author (see ^PipBase Info^).

If, for any reason, you're bored of being registered, type
PIP BOOST NULL

Important notice: since in your key there is (coded) your
name, you cannot modify user#0 after you required the key.

Remember that PipBase is shareware, and paying a
registration key is the best way to say Thank You to the
author.
*E
*B 103,BTCHANGE
PIP BTCHANGE zone net node point [CRASH|HOLD|NORMAL]

Valid only in a Binkley Term environment, renames (or
eventually merges) a .CLO/.CUT/.HLO/.HUT/.FLO/.OUT
(accordingly to the first priority given) for the
specified zone:net/node.point, changing its priority to
the second priority verb specified (if no priority is
given, NORMAL is assumed).
*E

*B 104,BTPOLL
PIP BTPOLL zone net node point [CRASH|NORMAL]

Valid only in a Binkley term Environment, generates a null
.FLO or .CLO file to force Binkley to call the node.

If no priority is specified, NORMAL is assumed by default.
*E
*B 105,BTREQUEST
PIP BTREQUEST zone net node point filename.ext
                                [CRASH|NORMAL]

Valid only in Binkley Term environment, generates a file
request for the given mode; if CRASH priority is specified,
a null .CLO file will be generated.

If no priority is given, NORMAL is assumed.
*E
*B 106,BTSEND
PIP BTSEND zone net node point \path\filename.ext
                              [CRASH|HOLD|NORMAL]

Valid only in a BinkleyTerm environment: generates a file
attach of the specified file to the specified node, with
the specified priority; if no priority is given, NORMAL
is assumed.

When Binkley will contact the node, the file will be sent.
*E
*B 107 BTUPDATE
PIP BTUPDATE zone net node point \path\filename.ext
                                [CRASH|HOLD|NORMAL]

Valid only in a Binkley term environment: sends an update
request to the specified node, with the specified
priority; if no priority is specified, NORMAL is assumed.

\path\filename.ext should be the name of an existing
file. When Binkley will call the node, it will reqeust
the file, but it will accept it only if newer than the
existing one.
*E
*B 108,CREATE
PIP CREATE is the command to create a message area.
Syntax is:
PIP CREATE area# "description"
    #LOCAL|#NETMAIL|#BAD|#DUPES
    message# day#
or
PIP CREATE area# "description" echotag message# day#
    origin#

Where area# is the area number, from 0 to the maximum
area number (see PIPBASE SET for informations about the
number of areas allowed for each model) that you defined
when you ran PIP ^SET^.

Description is a description of the contents of the area.
*P
Tagname is the echomail tag (if the area is an echo area,
a conference shared by multiple BBS; contact the Echomail
Coordinator or your boss for more informations), or the
keyword #NETMAIL (indicating an area for matrix
messages), #LOCAL (messages here will never be exported),
#BAD (if you want in this area all messages arriving with
unknown echotags) or #DUPES (defining an area to store
duplicate messages).

message# is the number of messages the area will contain.
If it is 0, the area treated as a Passthru area, and all
messages will be deleted immediately after a PIP
^EXPORT^. See ^PURGE^ for more informations.

day# is the maximum number of days the messages will stay
in your disk (see also PURGE).
*P
origin#: when you define an echomail area, you must
associate to it an origin, a phrase that will be appended
to each message to identify the sender's BBS; you've to
set a list of origins (see ^SETORIGIN^) and then
associate one of them to each area (see also
^PICKORIGIN^). If you're creating an echomail area,
remember to issua elso a ^SETEXPORT^ (see) command to
link the conference to all others BBSes and/or points.
*E
*B 109,DELETE
PIP DELETE area# message#

It deletes the message message# form the area number area#

Warning: it marks only the message as deleted, but it
doesn't erase it form the disk. You may recover it with
PIP UNDELETE or scratch it with PIPBASE PACK.

With PIP DELETE you may override the PIP LOCK option.

See also ^LOCK^, ^PACK^, ^PURGE^ and ^UNDELETE^.
*E
*B 110,DELROUTE
PIP DELROUTE rule#

This command removes the rule number rule# from the
routing file.

Rule numbers are assigned automatically when you run PIP
^ADDROUTE^ (see) and shown by PIP ^LISTROUTE^ (see).

Warning: when you execute a DELROUTE, all routing rules
are renumbered.
*E
*B 111,DESTROY
PIP DESTROY area#

This command destroys a message area.
All messages in the area will be lost, and the area
description will be removed form area list.

Be cautious!
*E


*B 112,EXPORT
PIP EXPORT

It seeks all the message base looking for new messages.
If there are new messages in exported areas (i.e.: in
netmail area, addressed to other nodes, or in echomail
areas, for which there are other nodes in the chain),
they will be packed accordingly to the ^SETFRIEND^,
^SETATTACHES^ (see), ^SETEXPORT^ (see) and ^ADDROUTE^
(see) directives.

When enabled (and unless your friend is marked as HOLD),
your mailer will deliver mail bundles.

When a message is packed in an outgoing bundle, it's
marked as "Sent". If it was a netmail (or matrix) message
marked as "Kill Sent", it will be also deleted.
*E
*B 113,GHOST
PIP GHOST

This command scans all your #NETMAIL area, sending a
receipt request for each message it founds, even if the
ReturnReceiptRequest flag is set to off.
A standard message is always generated; if you defined a
file with SETRR (see), that file will be appended to the
standard text.
It flags all processed mesages as Received.
Important: if you use PIP GHOST, you should'nt use also
PIP RR.
See also: ^RR^, ^SETGHOST^ and ^SETRR^.
This option is enabled in registerd version only.
*E
*B 114,HELP
PIP HELP [command]

To know all about a particular command or a setting, type
PIP HELP followed by the command you want to know all
about. If it's a SETxxxxx comand, you'll be informed also
on what means that setting.

You may navigate between help pages in hypertextual mode.

PIP HELP without parameters shows the command list.

Square backets are used to indicate optional parameters.
The pipe sign (|) means "choose one or another".

A # after a formal parameter indicates that the parameter
has to be a decimal number.

see: ^Pipbase help^ and ^Help on help^
*E
*B 115,INDEX
PIP INDEX [area#|DESTPTR]

This command regenerates PipBase index files.
It may be useful when they're corrupted.
If you specify the area number, only the index for the
specified area will be regenerated
Since Destptr.Pip is an unique index for all areas, it
will always be recreated for all areas: It's not a bug!

Important: in regenerating index files, PipBase cannot
know which messages were locked and which deleted, since
these informations were stored in the corrupted index
file, so you'll have to re-lock and re-purge the
messages. Don't use this option unless necessary.
*P
If you specify DESTPTR instead of an area number, only
DestPtr.Pip will be generated. This file contains only a
copy of the addressee names, and so a PIP INDEX DESTPTR
doesn't destroy any bit.
*E
*B 116,IMPORT
PIP IMPORT

It looks if there are mail packets in the inbound
directory, unpacks them and places them in the proper
message area.

If a message belonging to an undefined conference is
found, it will be placed in the #BAD area (if defined;
otherwise it will be lost).

Each conference is identified by a conventional tagname.

See also ^CREATE^ and ^EXPORT^.
*E
*B 117,INFO
PIP INFO

This command prints informations about the PipBase
project and its authors without forgetting
acknowledgements to all peoples that helped us in
developing this great product.

see: ^PipBase Info^
*E
*B 118,LINK
PIP LINK [area#]

Messages are sorted to make a "Reply Chain", i.e. to have
a linked list of all messages with the same subject; it's
useful with most editors.

A LINK (or a SORT) is suggested after each ^IMPORT^, or
once a day.
PIP ^PACK^ and ^SORT^ (see) perform automatically a LINK.
*E
*B 119,LISTAKAS
PIP LISTAKAS

It presents the list of all defined addresses.

Addess #0 is your main address; all others are "aka"s
(A.K.A.=Also Known As...) or secondary addresses.

It also displays the settings of the fakenet and of the
"UUCP" internet gateways

See also ^SETNODE^ and ^SETUUCP^
*E


*B 120,LISTAREA
PIP LISTAREA area# [NEW]

It lists all the headers of the messages contained in area
area#.

See ^READAREA^ for more information about the NEW switch.
*E


*B 121,LISTAREAS
PIP LISTAREAS [VERBOSE]

To see the area list.

Add the VERBOSE switch to know all about an area, and not
only the number and the description.

See also: ^LISTEXPORT^
*E


*B 122,LISTCFG
PIP LISTCFG

To know some general settings established by ^SETINBOUND^,
^SETOUTBOUND^, ^SETATTACHES^, ^SETPACKER^, etc. (see all
SETxxxxx and RESETxxxxx commands).

*E


*B 123,LISTEXPORT
PIP LISTEXPORT

To know where each area is exported. The list is in an
AREAS.BBS-like format: area number, spaces, area tag,
spaces, addresses of friends linked to the area, newline.

See also ^EXPORT^, ^SETEXPORT^, ^LISTFRIENDS^ and
^SETFRIEND^
*E


*B 124,LISTFRIENDS
PIP LISTFRIENDS

It lists all friend nodes set with ^SETFRIEND^ (see).
*E


*B 125,LISTORIGINS
PIP LISTORIGINS

It lists all defined origins, set by ^SETORIGIN^ (see).
*E


*B 126,LISTROUTE
PIP LISTROUTE

This command lists all routing rules defined with
^ADDROUTE^ (see).

*E


*B 127,LISTUSERS
PIP LISTUSERS

This command prints the list of first eight users of the
system, those - defined by ^SETUSER^ (see) - accessing the
PipBase from the console.

*E


*B 128,LOCK
PIP LOCK area# message#

It is used to "lock" a message, i.e.: to prevent it to be
deleted by PURGE (see).

Usually, it's useful for posting policies as the first
messages of an area and make them undeletable so that users
will never say "I didn't know the rules..."

See also ^DELETE^, ^PURGE^ and ^UNLOCK^
*E


*B 130,MARK
PIP MARK area# message#

It marks as "received" the specified message, i.e. it will
no longer be shown by PIP ^READAREA^ ... NEW (see)

*E


*B 131,MOVEAREA

PIP MOVEAREA old_area# new_area#

To change number to an area, you may use this command.

*E


*B 132,PACK
PIP PACK [area#]

It definitively removes deleted messages from the disk.
Usually, it's executed periodically, to avoid message base
growth over its limits (i.e. 32768 messages per area, or
less if you haven't a very large hard disk; Warning: I'm
not responsible for what will happen if you axceed that
limit!).

If you don't specify the area#, all areas will be packed.

It also renumbers the messages, re-establishing a
continuous numbering, and relinks it (see ^LINK^).

See also ^DELETE^, ^PURGE^ and ^UNDELETE^.
*E


*B 133,PICKORIGIN
PIP PICKORIGIN area# origin#

After you defined all your origins with ^SETORIGIN^ (see),
you must associate them to respective areas.

PICKORIGIN states that area number area# will have origin
number origin#; more than one area can have the same origin
(of course, because you can have up to 32768 areas and only
up to 256 origins); if you change an origin with SETORIGIN,
it will be modified for all areas.

Origins defined for each area are shown with LISTAREAS
^VERBOSE^ (see); the origin list is shown by ^LISTORIGINS^
(see).

*E


*B 134,POST
PIP POST area# filename.ext "from..."|user# "to..."|user#
   "subject" [zone net node point [PRIVATE] [HOLD|CRASH]
              [ATTACH|REQUEST] [KILL] [RR] [AUDIT]]

This complex command is necessary to send a message, i.e.
to put it into the PipBase.

First the message text has to be edited and placed in file
filename.ext; you may do this with any plain text editor.

Then, issue the command: area# is necessary, and is the
number of the area where the message will go; "from..." is
the sender's name (enclose it in quotes), but if he/she's
included in the user list set by ^SETUSER^ (see), you may
specify only his user number instead of the name;
similarly, "to..." is the name of the recipient of the
message.
*P
If you're sending a normal message, "subject" is a line
describing contents of your test; for a fileattach or a
file request, you'll know all later.

If choosen area is a #NETMAIL or matrix area (see
^CREATE^), you'll have to specify also the recipient's
address with the four numbers zone, net, node and point,
and you'll may specify one or more of the following flags:

PRIVATE: it means that the message is private, and cannot
be read by other peoples (notiche that the sysop can always
inspect every messages).
*P
HOLD means that the message (or file) will be held by your
system until the addressee's system will not call; CRASH is
the opposite, and means that the message will be delivered
as soon as possible by your system, calling directly the
addressee's node; if you don't specify neither CRASH nor
HOLD, the message will be treated as defined by ^ADDROUTE^,
^DELROUTE^ and ^LISTROUTE^ (see).

ATTACH: when ATTACH is used, you must place in the subject
not a simple line of text, but a file name (complete with
path): it means that the specified file will be sent along
with the message.

REQUEST is its opposite: it requires a file name as
subject, but without path, and the result is that the
specified file will be requested to the remote system.
File requests are never routed.
*P
KILL simply means that the message will be killed
immediately after sending.

RR is the Return Receipt Request. When it will arrive, if
the addressee has a return receipt processor such as
PipBase (registered), you'll have a receipt confirming the
arrival. Some mailers follow a new standard: to request a
return receipt you must place a *RR* string in the subject
(it is case- sensitive, and you've to put the asterisks).
If you do not know the standard followed by remote's
mailer, use both *RR* and RR.

AUDIT is an audit request. Sincerely, I don't know what it
means, but it is on FTS-0001, and I added it.

See also: the ^RR^ command and Pip ^REPLY^ message editor
help.

*E


*B 135,PURGE
PIP PURGE [area#] [NOINDEX]

It deletes old or received messages from the message base,
accordingly to the settings established with PIP ^CREATE^
(see) and shown by PIP ^LISTAREAS^ VERBOSE (see).

You may prevent the deletion of some messages by using the
PIP ^LOCK^ option (see).

If you don't specify the area#, all areas will be purged.

If you specify NOINDEX, the DestPtr.Pip index will not be
rebuilt. It means that a user will find with ^SCANX^ also
purged messages.
*P
NOINDEX is useful when PURGE is immediately followed by an
INDEX or by a PACK, that rebuilds the DestPtr index, to
speed up operations.

See also ^DELETE^, ^SETPURGE^, ^PACK^ and ^UNDELETE^.
*E


*B 136,READ
PIP READ area# message# [MARK|DELETE]

It presents the message number msg# of the area number
area#.

Area numbers are set with PIP ^CREATE^ (see) and shown with
PIPBASE ^LISTAREAS^ (see).

In each area, messages are numbered from 0 to 32767.

If you specify also MARK or DELETE, a PIP ^MARK^ (or
^DELETE^) will be performed on the message immediately
after the reading

See also ^UNDELETE^, ^UNMARK^ and ^REPLY^ commands.
*E


*B 137,READAREA
PIP READAREA area# [NEW] [MARK|DELETE]

This command prints on the screen all messages contained in
area area# or, if NEW is specified, all messages not yet
marked as received (it doesn't use "lastread" facility) or
deleted.

The switck MARK tells to mark as received all messages
printed; DELETE tells to PIP to delete them.

To stop scrolling, use the Pause or the Ctrl-S key of your
keyboard, or a MORE filter, or a 4dos | LIST /S

See also: ^SETLASTREAD^, ^SHOWLASTREAD^, ^READ^ and ^REPLY^
*E


*B 138,RESET5DMSGID
PIP RESET5DMSGID

This command disables any effect of the ^SET5DMSGID^
command (see).

*E


*B 139,RESETELIM4D
PIP RESETELIM4D

This command revokes the effect of ^SETELIM4D^ (see).

*E



*B 140,RESETREPLY
PIP RESETREPLY

This command disables ^^aREPLY kludge generation, i.e.:
the ^^aREPLY kludge will not (no longer) be added to
your replies.

See also ^SETREPLY^.
*E


*B 141,RESETEXPORT
PIP RESETEXPORT area# friend#

This command eliminates the specified friend form the
export list of that area, i.e.: it unlinks the node from
the conference.

It does not delete messages yet packed (exported) but still
in outbound directory.

See also ^SETEXPORT^ and ^LISTEXPORT^.
*E


*B 142,RESETROBOT
PIP RESETROBOT KILLREQUESTS|KILLANSWERS

This command revokes settings established with PIP
^SETROBOT^ (see it for more informations).

*E


*B 143,RR
PIP RR

This robot, enabled only in registered version, scans
#NETMAIL area for messages flagged with the
ReturnReceiptRequest flag (see PIP ^POST^ with parameter
RR) or containing the string *RR* in the subject and sends
a message (a "return receipt") confirming to the sender
that his/her message is arrived.

In addition to the standard receipt text, you may set a
file (with ^SETRR^) to be appended to the receipt message.

See also ^GHOST^ and ^SETGHOST^.
*E


*B 144,SCANX
PIP SCANX user# [area#]

Scanx search all message base for messages addressed to the
user number user#, and displays them (if found) on the
screen.

If the optional parameter area# is specified, then the
search will be limited to that area.

*E


*B 145,SET
PIP SET pipbase_dir logfile_name
    TINY|SMALL|MEDIUM|LARGE|EXTRA_LARGE

This is the first configuration command you've to issue. It
prepares the message base.

pipbase_dir is the directory where you want to store the
  message base

logfile_name is the name of the file where all PipBase
  operations will be logged; usually it's PB.LOG; insert
  NUL if you don't want any log

Last keyword is the desired model, or the size of the
  message base: TINY means 64 message areas, SMALL 256,
  MEDIUM 1024, LARGE 4096 and EXTRA-LARGE 32768.
*P
Choose the size accordingly to your needs and the capacity
of your disk.

See also ^SETPIPDIR^, ^SETLOGFILE^, ^SETLOGLEVEL^ and
^SETLOGTYPE^

*E


*B 146,SET5DMSGID
PIP SET5DMSGID

This command forces PipBase to insert the domain (fifth
dimension) in the CTRL-aMSGID: kludge.

Using it is necessary only if you are linked to
inter-network conferences, but it wastes bytes in
trasmissions and may couse incompatibilities: don't use it
unless necessary.

See also ^RESET5DMSGID^
*E


*B 147,SETAREAAKA
PIP SETAREAAKA area# aka#

If you're in more than one network, you must use this
command to tell PIPBASE which address will go in the origin
line of any echomail message of the area.

area# is the number of the area you want to set, and aka#
is the number (in the address list - see ^LISTAKAS^) of the
address you want to use in that area.

*E


*B 148,SETAREAFIX
PIP SETAREAFIX friend# password level#

This command enables friend number friend# to making
requests to AreaFix (see PIP ^AREAFIX^) with password
"password".

To the friend is associated a level, level#, between 0 and
255; you may prevent the friend to link some areas by
setting the friend level lower than the area level.

Area levels are set with ^SETAREALEVEL^ (see).
*E


*B 149,SETAREALEVEL
PIP SETAREALEVEL area# level#

You may assign a level to every area; level# is a number
between 0 and 255 and is used to protect indiscriminated
access to some areas.

By default, the level of a newly created area is 0, i.e.
all users can read, write and areafix it.

See also ^SETAREAFIX^.
*E


*B 150,SETAREANAME
PIP SETAREANAME area# "area description"

This command changes the description you assigned to an
area using ^CREATE^.

*E


*B 151,SETAREANOTES
PIP SETAREANOTES area# "area notes"

This command sets additional notes on an area.
Additional notes are a line of comment or of special
kludges used by other programs.

*E


*B 152,SETATTACHES
PIP SETATTACHES netmail_directory FRODO|D'B|BINK
  [PACK[-MATRIX]|DYNA[MIC-PACKING]]

you must inform PipBase on how it has to communicate with
the front end, i.e. with the program that handles modem
connections.

netmail_directory is the directory where your front end
holds matrix messages, fileattaches and filerequests.

FRODO and D'B specify that your mailer uses netmail
messages to carry fileattaches; in this case, do NOT delete
strange netmail messages.
*P
Most famous programs using this fileattach style are Front
Door and D'Bridge.

BINK are to use PipBase with *.FLO fileattaches, as Binkley
Term and MilqueToast do. In this case netmail directory is
not used.

Optionally, you may specify if matrix messages have to be
packed by PipBase [PACK-MATRIX] or left to the front end
[DYNAMIC-PACKING]. For D'Bridge and Front Door it's
indifferent; Binkley needs PACK-MATRIX (DYNAMIC-PACKING is
legal but then, you'll have to use an external program such
as Qmail, Wmail or Ommm to process netmail messages.

If you leave DYNAMIC-ROUTING, you don't need to define a
route with ^ADDROUTE^.

*E


*B 153,SETELIM4D
PIP SETELIM4D

Some old (like Qmail) or buggy mailers don't accept
4-dimensional informations in SEEN-BYes and PATHs; with PIP
SETELIM4D, you tell to PipBase to hide 4D informations and
leave only 3D standard addresses.

This parameter is not used when a fakenet is used.
If you're a point of a 4D boss, do NOT set this, or you'll
see all your messages doubled! For a fakenet point, this
parameter may or may be not necessary (it depends on what
program does your boss uses; Wmail and PipBase are
certified: SETELIM4D not necessary; for others let's try
and establish it with your boss.
If you're a boss node, set this accordingly to your up/down
links (use PIPBASE SETELIM4D if you're surrounded by
old-style 3D processors, PIP ^RESETELIM4D^ if they all have
new packers.
*E



*B 154,SETEXPORT
PIP SETEXPORT area# friend#

This command tells PipBase to export an echomail area to a
friend, i.e. to send him copies of all messages written in
that area or arriving from other nodes.

It's valid only in "echomail" areas (also known as
conferences).

Notice that only new messages (not also the messages yet
written) will be sent, and that they're sent only when you
perform a PIP ^EXPORT^.

See also ^RESETEXPORT^, ^CREATE^, ^EXPORT^, ^LISTEXPORT^,
^LISTFRIENDS^ and ^SETFRIEND^.

*E


*B 155,SETFAKE
PIP SETFAKE fakenet#

If you're a point, your boss will explain you the use of
the so-called fakenet (or fake-address); so, probably, it
will be bored of using this antiquate method for addressing
points.

If you're a boss system, why to use fakenet? Full
4-dimensional addressing is better! In some regions, there
are rules to establish the fakenet, so, if you cannot do a
better choice (problems with old points), ask your network
coordinator.
*P
Warning: this command requires only the fakenet number, not
the complete fake address; the zone and the point number
are taken from the first address in the address list (e.g.:
if you are 2:334/306.666 and your boss uses fakeaddress
24306, you've to issue PIP SETNODE 0 2 334 306 666 and then
PIPBASE SETFAKE 24306).

If you don't specify a SETFAKE, 4D-addressing will be used;
to stop 3D- operations and return to 4D after a SETFAKE,
type PIP SETFAKE 0.

Notice that now also Binkley Term 2.50 can handle 4D
addressing.
*E


*B 156,SETFRIEND
PIP SETFRIEND friend# zone# net# node# point# packer
    parameters [HOLD|CRASH]

This informs the PipBase system that a node is your
"friend" i.e. that you regularly exchange mail with it.

You need to define with SETFRIEND all nodes you export
echomail to, and all nodes you route netmail via.

friend# is a progressive number from 0 to 255.

zone#, net#, node# and point# are the network address of
  the node: contact the network administrator (if you're
  a BBS) or your boss (if you're a point) if in doubt.
*P
packer is the name of your favourite packer, like PkZip,
  Arj, LhArc, etc. Be sure that the node you send mail to
  supports that packer (It has to support Arc, and so
  specify it if in doubt. Contact the system operator to
  know if he admits something better).
  You've to specify the extension .COM or .EXE.

parameters are passed to the pacher before the name of the
  archive name. Enclose them in doble quotes if they're
  more than one. They depend from packer. by example:

  PkZip.Exe -eax
  LhArc.Exe "a -m"
  PkPak.Exe -a
*P
The HOLD switch specifies that you'll never call that node:
you'll wait his call to send him his mail; CRASH means that
mail for the friend will be sent immediatly when packed

See also ^SETEXPORT^ and ^ADDROUTE^.
*E


*B 157,SETGHOST
PIP SETGHOST "Ghostwriter's name"

When the Ghostwriter, invoked by RR or GHOST, sends a
receipt message, it usually signs as "PipBase GhostWriter".
If you want to made him signing with another name, like
"Pasquini's Ghostwriter" (Stefano Pasquini, REC 2:33, is
famous for his ghostwriter - "The spirit of italian
fidonet"), You may set another name using this function.

See also ^RR^ and ^GHOST^
*E


*B 158,SETINBOUND
PIP SETINBOUND directory_name

This command is to set your inbound file directory, i.e.
the directory where your mailer puts files just received
from another node.

Front Door and D'Bridge aficionados call it "File"
directory, Opus-dependent people call it "Inbound"
directory and Binkley Term lovers use the term "Mail File"
directory as well as "Inbound". Dont' get confused and set
it identically as it is in your mailer setup!

See also ^SETOUTBOUND^, ^SETATTACHES^ and ^LISTCFG^.
*E


*B 159,SETLASTREAD
PIP SETLASTREAD user# area# message#

Each user has a bookmark, called the "lastread pointer",
for each area. With SETLASTREAD, the user number user# may
move his lastread pointer in the desired area to the
desired message.

See also ^SHOWLASTREAD^.
*E


*B 160,SETLOGFILE
PIP SETLOGFILE filename.ext

This overrides the log file name defined with PIP ^SET^
(see).

You may also specify a full path name, with directory.

See also ^SETLOGLEVEL^ and ^SETLOGTYPE^.
*E
*B 161,SETLOGLEVEL
PIP SETLOGLEVEL 0|1|2|3

You may want a less or more detailed log file.

To have a very detailed log file, specify a 3; for a
shorter log, specify 0 1 and 2 are intermediate solutions.

See ^SET^ to know what the log file is, and also
^SETLOGFILE^ and ^SETLOGTYPE^.

*E


*B 162,SETLOGTYPE
PIP SETLOGTYPE BT|FD

There are two styles in writing the log file: BT for a
Binkley/Opus style and FD for Front Door/D'Bridge style.

The former is more linear; the latter is more compact.

Since de gustibus non est disputandum, try both and then
make your choice.

See also ^SETLOGFILE^ and ^SETLOGLEVEL^.
*E

*B 163,SETNODE
PIP SETNODE aka#|0 zone# net# node# point# domain

If you're in a network, you must have an address (or more
than one). PipBase allows up to ten different addresses,
numbered from 0 to 9. Address #0 is the main address.

An address is composed by four numbers: zone# net# node#
and point#, and a string, called domain. Usually they're
printed in the "fidonet" format zone:net/node.point@domain.
When point is 0, it's often omitted. Addresses are assigned
by the network coordinator (or by the boss if you're a
simple point): ask him!

aka# is the number of the address you're specifying. Other
parameters are the fields of the address

See also ^SETFAKE^ and ^LISTAKAS^.
*E


*B 164,SETORIGIN
PIP SETORIGIN origin# "origin text"

On every echomail message, near the end, there is a sort of
banner, stating where the message comes from, called the
"origin".

Each sysop, or point, has his origin. You may change
frequently origin, and have different origins for different
areas.

With PipBase, you must define an origin list, from which
you (or the random system) will choose the origin to be
associated to an area. This function is performed by
SETORIGIN.
*P
origin# is the number of the entry in the origin table,
from 0 to 255; ^LISTORIGINS^, ^PICKORIGIN^ and ^CREATE^
will refer to this code.

origin text (remember to enclose it in double quotes) is
the text of the banner, not including the fixed prefix " *
Origin: " and your address (that will be added by default
at the end of the origin text.

Usually, an origin is one of the most powerful ways to
manifest a point's creativity

*E


*B 165,SETOUTBOUND
PIP SETOUTBOUND directory_name

This command is to set your outbound file directory, i.e.
where the outgoing mail is stored, waiting to be sent.

Set it as it is in your mailer setup. Notice that some
mailers double it as "Outbound" directory and as "ArcMail"
directory.

See also ^SETINBOUND^, ^SETATTACHES^ and ^LISTCFG^.
*E


*B 166,SETPACKER
PIP SETPACKER packer.ext "parameters"

This command sets your default mail packer and the
parameters to run it.

Since all nodes must be able to unpack mail compressed with
the default packer, it's usually set to an .ARC-compatible
packer, such as ARC or PKPAK.

You must specify proper .COM or .EXE extension too, and
parameters to be passed for right operations.

See also ^SETFRIEND^.
*E


*B 167,SETPACKERDIR
PIP SETPACKERDIR drive:packer_directory

Unless you've all your file packers and all respective
unpackers in a directory pointd by the PATH environnement
variable, you must declare here with SetPackerDir where
they can be found.

Packers supported are PkPak, PkUnPak, PkArc, PkXarc, Pak,
Arj, Zoo, LhArc, LhA, Squeeze-It, PkZip and PkUnZip.

*E


*B 168,SETPIPDIR
PIP SETPIPDIR pipbase_directory

If you want to move all your message base from one
directory to another, you must also inform PipBase of that,
using the SETPIPDIR command to tell what is the name of the
new directory (eventually complete with drive
specifications).

This command modifies the value set with PIP ^SET^ (see),
but does NOT move files from a directory to another: you
must do that manually.

*E


*B 169,SETPURGE
PIP SETPURGE area# messages# days#

When you CREATEd area number area#, you specified some
criteria for deleting old messages; with SETPURGE you may
modify them. area# is the number of the area you want to
modify; other parameters are discussed in ^CREATE^ and
^PURGE^ sections (see).

*E
*B 170,SETREPLY
PIP SETREPLY

This command enables ^^aREPLY kludge generation, i.e.:
the ^^aREPLY kludge will be added to your replies

See also ^RESETREPLY^.
*E
*B 171,SETROBOT
PIP SETROBOT KILLREQUESTS|KILLANSWERS

Pipbase has some robots in it. Robots are procedures that
execute commands when a #NETMAIL message is addressed to
them, and they may answer with a message.

You may keep all messages directed to, and coming from,
robots, or let robots delete them when processed.
By default, they aren't killed; if you issue PIP SETROBOT
KILLREQUESTS, all messages from users to robots will be
killed; if the parameter passed is KILLANSWERS, all
messages written by robots will be flagged as KILL/SENT
(see PIP POST).

To return to keeping track of messages, you'll have to
issue a PIPBASE ^RESETROBOT^ (see).

Robot settings are shown by ^LISTCFG^ (see).
*E
*B 172,SETRR
PIP SETRR return_receipt_file|NULL

This specifies the file to be used to send the return
receipt with PIP ^RR^ (see).

It is not necessary, because there's a standard message. If
you specify it, it will be appended to the standard text.

return_receipt_file is the name (complete with path and
extension) of an existing plain ASCII file.

To return to the standard message, simply type PIP SETRR
NULL
*E


*B 173,SETTAG
PIP SETTAG area# tagname

If you want to change the echotag to an area, use this.

area# is the number of the area you want to change; tagname
is the new tag.

If you specify #NETMAIL or #LOCAL for tagname, the area
will not still be an echomail area.

A tag change does not affect ^SETEXPORT^ values.

See also ^LISTEXPORT^, ^CREATE^ and ^EXPORT^.
*E


*B 174,SETTEAR
PIP SETTEAR "tearline text"

The tearline is a line added to every echomail message,
near the end, preceeded by three minus sign ('-'), to tell
to the world that you use a certain program.

Pip*'s tearline always contains the name Pip*, the version
number and your registration number (or the "demo" string
if you're unregistered; see BOOST for explanations), but
you may add the name of another product, such as PipRog, or
the name of an utility of yours (to do a little commercial
spot). Simply specify the string you want to add between
double quotes, like PIP SETTEAR "+ VVreply 0.99"

*E


*B 175,SETTEMPDIR
PIP SETTEMPDIR temporary_directory

PipBase needs sometimes to write on disk lots of datas, to
delete them a few instants later.

With SetTempDir you specify where to store these temporary
datas. I suggest to place this directory on your fastest
device, but be sure that, especially for RAM disks, there's
enough space (some hundreds of Kb are a large device for a
point; at least a megabyte is needed for a BBS, and more
than one if it has a lot of points or it's a hub or host.

*E


*B 176,SETUNPACKER
PIP SETUNPACKER jolly_unpacker_program "parameters"

This command sets the useful "Jolly unpacker", an unpacking
program to use when PIP does not recognize the packer that
created the incoming bundle.

Parameters are the same as for PIP ^SETPACKER^ (see).

You may place here a general unpacking program like GUS, or
any new unpacker, other than PkUnZip, PkXArc, Arj, Lha,
Squeeze and Pak, like XArcPlus, that you know your
feeder is using.

*E


*B 177,SETUSER
PIP SETUSER user# "user name"|NULL

PipBase needs an internal user list of the system
operators, i.e. of those users accessing the message base
directly via Pip.Exe.

These users are numbered from 0 to 7, and you set each of
them with a SETUSER command; the list is shown by
^LISTUSERS^ (see).

Be aware that the user # 0 has to be the legal sysop,
whose name is on the registration key.

To remove an user from list, use PIP SETUSER n NULL

See also ^Setup\Users^ in menu mode
*E


*B 178,SETUUCP
PIP SETUUCP outbound_zone net node inbound_zone net node

PipBase and PipReply can transparently handle internet
messages, using the UUCP gateways.

This is not the proper site for a complete tractation of
internet messages, but if you want to use them, let PipBase
know the IFNA-style addresses of the outbound (i.e.: IFNA
style network -> UUCP) and inbound gateway (UUCP -> IFNA).

IFNA addresses are of the form zone:net/node.

To know these addresses, ask the gateway administrator or
an internet guide.

Warning: DO NOT TOUCH THIS COMMAND UNLESS YOU KNOW WHAT
YOU'RE DOING!
*E
*B 179,SHOWLASTREAD
PIP SHOWLASTREAD user# area#

This command displays where user number user# placed his
bookmark in area area# (remember that an user has as a
bookmark in every area...)

See also ^SETLASTREAD^.
*E


*B 180,STAT
PIP STAT [user#]

Stat provides some statistics on the message base, simply
displayed.

If you specify an user number, PIP will display an asterisk
for every area containing unread messages; this option uses
lastread bookmarks (see ^SETLASTREAD^).
*E


*B 181,UNDELETE
PIP UNDELETE area# message#

It recovers message number message# from area area#, where
it was accidentally deleted.

After a PIP ^PACK^ (see), you'll never recover any message.

See also PIP ^DELETE^.
*E


*B 182,UNLOCK
PIP UNLOCK area# message#

This command revocates the locking established by PIP
^LOCK^. After its execution, purge will be able to delete
the message.
*E


*B 183,UNMARK
PIP UNMARK area# message#

To reset the "received" flag from the specified message.

See also ^MARK^.
*E
*B 184,SORT
PIP SORT [area#]

This command will sort messages accordingly to their date.

If you specify an area number, only the specified area will
be sorted.

I suggest to perform always a PIP SORT after a PIP ^IMPORT^

PIP ^PACK^ maintains time ordering; PIP ^INDEX^ destroys it,
so you'll have to reorder a SORT after an INDEX.

Note: only unread messages will be sorted.

A PIP SORT will always cause a PIP ^LINK^ command to be
executed.
*E
*B 200,REPLY
PIP REPLY [[/M=]area#] [/U=user#] [/25] [/NOEMS]

This command invokes the full-screen message reader/editor.

Specify /M=area#, where area# is a valid area number, to
enter directly into that area.

Specify /U=user#, where user# is a valid user number (see
^LISTUSERS^ and ^SETUSER^ for more info about PipBase
users) to tell to Pip Reply that you want to use the
user's pointers (for message scanning - see ^SCANX^
command - and lastread marks - see ^SETLASTREAD^ and
^SHOWLASTREAD^).

See also: ^Basic Pip Reply Topics^ and ^Mail\Reply^ help
screens.
*P
The ^/25^ switch means that you want to enter PipReply in
25-rows mode even if you set a 43 (EGA) or 50 (VGA) lines
mode in ^Setup\Viewer^.
*E
*B 201,Basic Pip Reply Topics
Pip Reply is the full-screen message reader/editor
integrated in Pip*.

Please select one of the following items:

^Pip Reply main screen^
^Pip Reply area selection^
^Pip Reply message list^
^Pip Reply change message^
^Internal text editor^
^Help on help^
*E
*B 220,Pip Reply area selection
Message area selection.

Select the message area you want to enter by clicking
on the area name with the mouse or by selecting it with
cursor keys and [Enter].

If you enabled it, areas containing unread messages are
highlighted by an asterisk.

[Esc] returns to the previously selected area.
[S] leaves editor.
[J] opens a ^Shell to operating system^.
[U] shows areas containing unread messages even if you
    disabled this option in ^Setup\Viewer^
*E
*B 221,Shell to operating system
If you open a shell to the operating system, yuo'll be
able to issue operating system (i.e.: DOS) commands.

With the MS-DOS command EXIT, you'll re-enter Pip*,
exactly at the point you left your work.
*E
*B 222,Pip Reply message list
Pip Reply message list

In this screen you can browse, select and delete messages.

Select a message with cursor keys and press [Enter], or
point it with the mouse and then click on TEXT button, or
double click the message to go to that message.
Select a message with cursor keys and press [Del], or point
it and click on DELETE button, to delete/undelete it.
Click on up and down buttons, or use [PgUp]/[PgDn] keys to
scroll message list and see other pages.
Click on ABORT button or press [Esc] to return to the
text-viewing screen without changing message.
Press [?], [F1] or click on HELP button to have this screen.
Press [J] to ^Shell to operating system^, or [S] to exit
PipReply.
*E
*B 223,Pip Reply change message
Change message
In this Pip Reply screen, you may change the message
before posting it. You may use following keys:
[F] change sender's name
[T] change recipient's name (and address, if area is
    netmail)
[S] change subject
[A] change area
[O] ^change origin^ line, if area is echomail
[B] change message text (body)
[Space] or [Enter] (or click on OK button): saves the
    message
[1] apply ^ROT-13^ to message text
[:] ^Carbon-Copy^ send (enabled only when posting a new
    message (and not when modifying an existing one)
*P
[?] or [F1] this help
[X] or [Esc] abort message
[J] opens a ^Shell to operating system^.
See also ^Flags^ screen
*E
*B 224,Flags
With this menu you can toggle all these message flags:
[P] private: only the addressee (and his sysop) will be
    able to read it
[C] crash: the message will be delivered immediately with
    a direct call
[H] hold: the message will wait until the addressee will
    call your system
[K] kill sent: the message will be deleted after sending
[E] file attach: the file indicated in the subject will
    be sent with the msg.
[Q] file request: the file(s) specified in the subject
    will be requested to the system that will receive the
    message; if it has a password to request files, place
    the password after the file name, separated by a bang
    (!); you cannot enter a complete path
*P
[U] update request: like [Q], but the file will be sent
    only if it is newer than the corresponding existing
    file on your disk; you must give a complete path
[R] ReturnReceipt requst: it indicates that you want a
    return receipt for your message; not all mailers
    handle it, and there is also an alternate way to
    request a return receipt: by placing a *RR* in the
    subject line (see also PIP ^RR^ command)
[I] audit request: when you request the "audit" for your
    message
[S] is return receipt: it is considered like an answer
    generated by a ghost writer (like PIP RR or PIP ^GHOST^)

Warning: in echomail areas you cannot use all these flags:
they work only in #NETMAIL and #LOCAL areas.
*E
*B 225,Pip Reply main screen
When in Pip Reply main screen (message-viewing), you can
use all these keys:

[<-] or [P] previous message
[->] or [N] next message
[PgUp] or [L] repeat last page
[PgDn] or [C] next page
[Home] or [<] goto first message
[End] or [>] goto last message
[G] goto message number...
[+]/[-] follow reply chain
[Ctrl-End] message pointed by lastread pointer (see
                      ^SETLASTREAD^ and ^SHOWLASTREAD^)
[A] change area (see ^Pip Reply area selection^ screen)
[4] scan messages for me
[T] view message list (see ^Pip Reply message list^ screen)
*P
[M] modify message (see ^Pip Reply change message^
    screen)
[R] reply to the current message
[Ins] or [I] insert a new message
[Canc] or [D] delete/undelete message (see ^PIP DELETE^)
[K] lock/unlock current message (see PIP ^LOCK^)
[F] forward to...
[X] export to file
[V] invoke the ^External Viewer^ to see the text
[!] view/hide kludges
[J] jump to DOS (see ^Shell to operating system^)
[?] or [F1] this page (see ^Help on help^)
[S] or [Esc] stop reading (exit form editor)
[1] crypt/decrypt messages using ^ROT-13^ algorithm
[U] ^uudecode^s files contained in the message
[Enter]: the ^JOLLY^ key
*P
[H] performs a text search over the message area,
    looking for a message containing a string in its
    header or in its body; warning: the search is
    case-sensitive; this option is enabled only in
    registered version
*P
Most of these commands are also accessibles by clicking
with mouse on the buttons placed near the border of the
screen: click on the current area display (at lower-left
corner) to change area; on the current message display
(center-bottom) to specify a new message number to jump
to; [<<<], [ < ], [ > ] and [>>>] (center-bottom) to go to
the first, previous, next and last message; [OFF] (top-
right) to leave Pip Reply; the reply chains (top-right) to
browse a message thread.

To scroll text, you may use also "hidden buttons": they
are not visibles, but the're active:

The text is divided in seven areas (approximately shown on
the next page):
*P
            Message header
╔═════════╤════════════════╤═════════╗
║         │ previous page  │         ║
║ previous├────────────────┤ next    ║
║         │ up a line      │         ║
║ message ├────────────────┤ message ║
║         │ down a line    │         ║
║         ├────────────────┼─────────╢
║         │ next page      │  ^JOLLY^  ║
╚═════════╧════════════════╧═════════╝
               Last line
*E
*B 226,Internal text editor
Pip Reply incorporates a little text editor to write
messages. We reccomend to use an external, more powerful,
editor, if you can, by simply placing your favourite
editor's name in the apposite field of the setup option,
but if you want to use this one, here you are the special
commands:

[Ctrl-J]: shell to DOS
[Ctrl-R]: crypt/decrypt line with ^ROT-13^ (for registered
          users only)
[Ctrl-Y]: delete line
[Ctrl-Z] or clicking on SAVE: save and terminate message
[Esc] or clicking on ABORT: abort message (without saving!)
[F1] or clicking on HELP: this help screen
*E
*B 227,JOLLY
The jolly key.

Only a key need an approfondite explanation: the enter
key, whose meaning changes, to be always the "Magic" key:
in a standard work session you'll use nearly always only
enter!

When selecting an area for the first time (i.e. when you
omitted the /M=nnn parameter), press only enter to enter
area #0; after, when you're at the "Select area:" prompt,
press enter to go to the next area.

When browsing messages, if you're in the body of a
message, press Enter to scroll the message (here,
Enter=C=PgDn); if you're at the end of the message, press
Enter to go to the next message (here, Enter=N).
*P
After having edited a message, Enter posts the message
without changing subject, origin, area, etc; if you
modified origin line, press Enter again to save it.

When you try to continue after you read the last message
in an area, if you enabeld it in the setup screen, you'll
be prompted for an area change; press enter to go to the
choose area menu.

In Pip Reply main screen, the hidden button near the
lower-right corner of the screen works exactly like
Enter.
*E
*B 228,ROT-13
The ROT-13 crypt/decrypt algorithm

ROT-13 is a standard way of hiding message text by
crypting it. They're not really crypted since everyone
who has a ROT-13 compatible editor can read them by simply
pressing a key, but it can be usefully used to hide puzzle 
solutions, or so.

A message crypted by applying ROT-13 can be decrypted with
a second application of the same procedure.

Let's see how does it work with the words of my friend 
Michele Pianta' (who implemented an external utility to 
crypt/decrypt messages with PIP, before I introduced this 
function in my program).
*P
It simply shift the ASCII code of alphabet characters of 13 
positions, remaining in the alphabet. Oh, damn! It's 
uncomprehensible! Well, it swaps 'A' with 'N', 'B' with 'O' 
... and vice versa (and 'a' with 'n', 'b' with 'o'... and 
vice versa).
*E
*B 229,Registered Users Only Option

    THIS OPTION CAN BE USED ONLY BY REGISTERED USERS!

To know how to register, see ^What About Registering?^ help
page.
*E
*B 229,Carbon-Copy
Carbon-Copy send

When you want to send a message to more than one people in 
the same area, you may use CC: (read Carbon-Copy) send 
option: compose the message, addressing it to the first 
recipient then press : or click on the CC: button: the 
message will be sent and you'll be asked about another 
recipient name; insert the second name and repeat sending 
until you've finished.

You'll have to send the last copy of the message with OK 
(Enter).

Messages already sent with CC: aren't stopped with an Abort 
(Esc) command.

This option is available only to registered users.
*E
*B 230,change origin
Change Origin Screen

When you want to change origin, a selection screen will 
appear, listing all defined origins.

Select the one you want with cursor-keys and Enter, or 
with a mouse click (click on scroll buttons at the top 
right corner to scroll with mouse).

If you want to create a new origin, press Ins: the origin
will be added at the first free place, and then selected.

If you want to alter an origin, select it with cursor keys
and then press space. Then edit it and press Enter.
*E
*B 231,uudecode
Uudecode

There is a method to encrypt binary files into message 
text; this method is called uuencoding.

To extract the file from the message text you must
"uudecode" it. This is done by pressing U from Pip Reply
main screen. If a file is contained in your current 
message, it will be written in the current directory.

To encode files, you'll have to get an uuencode utility
(there are some versions in public domain software).
*E
*B 232,CC: disabled
Carbon-copy send is not enabled when modifying a message.

See also: ^Pip Reply main screen^ and ^Carbon-Copy^
*E
*B 250,Yes or not?
Press Y for Yes or N for not, or click on the proper
button, or select the answer with cursor keys and press
Enter.
*E
*B 300,Pip General Menu
From this menu you may select one of the following
options:

^Program\About^        ^Program\Shell^       ^Program\Exit^

If a ^Binkley Term^ installation is detected (i.e.: if there
is a Binkley.Cfg file in the current directory), you'll
have also these options:

^Program\Terminal^                      ^Program\Poll Boss^


See also ^PipBase Info^ and ^PipBase Help^
*E
*B 301,Program\About
Option About from menu General

This option displays a window wiyh some informations about
Pip*.

You may always recall this window, while in Pip menu, by
pressing Alt-A.
*E
*B 302,Program\Shell
This option opens a ^Shell to operating system^.

You may always recall this window, while in Pip menu, by
pressing Alt-J.
*E
*B 303,Program\Exit
This options stops Pip* execution and returns to the
operating system prompt.

You may always exit, while in Pip menu, by pressing Alt-X.
*E
*B 304,Program\Terminal
If Pip* founds ^Binkley Term^ installed, you may run BT
directly from this menu with this option.

This command usually enters the Binkley Terminal emulation
mode.

Warning: for Binkley Term to be operative, it is important
that you load a ^Fossil Driver^ BEFORE you start Pip*.
*E
*B 305,Program\Poll Boss
If Pip* founds ^Binkley Term^ installed, you may run BT MAIL
directly from this menu with this option.

This command forces Binkley to poll immediately your Boss (it
is the BBS you get mail from, if you're a point).

Warning: for Binkley Term to be operative, it is important
that you load a ^Fossil Driver^ BEFORE you start Pip*.
*E
*B 380,Binkley Term
Binkley Term is a freely available program from Bit Bucket
Software, made for mail and file exchanging via modem.

Pip* is epecially made to be interfaced with Binkley Term
(also called BT).
*E
*B 381,Fossil Driver
A Fossil Driver is a device driver that replaces BIOS
functions for serial port handling.

Most communication programs require a Fossil Driver, and
most of these drivers are freeware or shareware.

Among them I suggest X00, BNU and DRCOMM.
*B 399,About Screen

                         Pip* 2.0

            Integrated message processor/editor

                  by R.Piola, 1991-93

*E
*B 400,Pip Mail Menu
From this pull-down menu, you may run all options relative
to mail operations.

^Mail\Reply^                ^Mail\Import^
^Mail\Export^               ^Mail\Link^
^Mail\Purge^                ^Mail\Pack^
^Mail\Return Receipt^       ^Mail\Ghost Writer^
^Mail\Rebuild Indexes^      ^Mail\Statistics^
^Mail\Sort^


See also ^PipBase Info^ and ^PipBase Help^
*E
*B 401,Mail\Reply
Mail\Reply
This option, always accessible via the Alt-E hotkey, runs
the message reader/editor Pip Reply.

See the PIP ^REPLY^ command and the ^Basic Pip Reply Topics^
screens.
*E
*B 402,Mail\Import
Mail\Import
This option, always accessible via the Alt-I key, performs
a PIP ^IMPORT^ (see) command, i.e.: unpacks the mail you
have in the inbound directory.

When finished, Pip* waits for a keypress before returning
to the main menu, to let you see what is displayed.

After importing mail, you should run also a ^Mail\Link^
command.
*E
*B 403,Mail\Export
Mail\Export
This option, always accessible via the Alt-O key, performs
a PIP ^EXPORT^ (see) command, i.e.: packs all messages you
wrote and places them in the outbound directory, ready to
be sent to other network sites.

When finished, Pip* waits for a keypress before returning
to the main menu, to let you see what is displayed.

You should always run an export before you poll your boss.
*E
*B 404,Mail\Link
Mail\Link
This option, always accessible via the Alt-L key, links all
reply chains: every message will have two pointers: one to
the preceeding message and ont to the following message
with the same subject.

It's the same as the command-line PIP ^LINK^ (see) command.

You should always run a link after you ^IMPORT^ed mail
*E
*B 405,Mail\Purge
Mail\Purge
This option, always accessible via the Alt-P key, scans the
message base and marks as deleted (see PIP ^DELETE^) all old
messages.

It's equivalent to the command line PIP ^PURGE^ (see).

After a purge, you should always run a ^Mail\Pack^ command
(see).
*E
*B 406,Mail\Pack
Mail\Pack

This command is equivalent to the PIP ^PACK^ command line
(see): it physically eliminates deleted messages.

Execute it periodically along with a PIP PURGE, if you
don't want an incontrollate growth of the message base
(well, Pip* hasn't troubles to handle message bases up to 2
Gigabytes, but maybe your hard disk has some problems).
*E
*B 407,Mail\Return Receipt
Mail\Return Receipt

This command activates the Return Receipt processor.

It scans your #NETMAIL area and sends an answer to all
messages flagged as Return Receipt Request.

It's equivalent to the PIP RR command line.

See also: PIP ^RR^, ^POST^, ^Setup\Robots^ and ^Flags^
*E
*B 408,Mail\Ghost Writer
Mail\Ghost Writer

This command is equivalent to the PIP ^GHOST^ command line.

It scans all your #NETMAIL message area and answers to
all messages addressed to you.

See also ^Setup\Robots^
*E
*B 409,Mail\Rebuild Indexes
Mail\Rebuild Indexes

This command, equivalen to PIP ^INDEX^ (see), regenerates
all PipBase index files.

Use it only if index files are corrupted, since it loses
the Locked and the Deleted flags.
*E
*B 410,Mail\Statistics
Mail\Statistics

This command displays some statistics about the message
base.

It is equivalent to the PIP ^STAT^ (see) command line.
*E
*B 411,Mail\Sort
Mail\Sort

This command sorts by date all unread messages.

It is equivalent to the PIP ^SORT^ (see) command line and
it's enabled only in registerd versions.
*E
*B 500,Pip Setup Menu
From this pull-down menu, you may configure all Pip*
functions.

^Setup\General^              ^Setup\Directories^
^Setup\Message Areas^        ^Setup\Origins^
^Setup\Network Addresses^    ^Setup\Friends^
^Setup\Routing^              ^Setup\UUCP Gateway^
^Setup\Users^                ^Setup\Robots^
^Setup\Log File^             ^Setup\Editor Preferences^
^Setup\Quotes^               ^Setup\Colors^
^Setup\Viewer^

See also ^PipBase Info^ and ^PipBase Help^
*E
*B 501,Setup\General
Setup\General

In this setup screen you can see the message base size (in
number of areas) that cannot be changed (it's set when you
create the message base with a PIP ^SET^ (see) command).

You may edit these parameters:

Remove Unuseful Kludges: when set to Y, Pip* will
eliminate from message base some unuseful kludges, saving
a little space. Warning: since eliminated kludges will not
be sent to all your downlinks, enabling this option is
ILLEGAL in some networks.
*P
Remove "Re:" from subjects: when this option is enabled
(set to Y for Yes), Pip* will attempt to strip the "Re:"
string that some editors append to the subject of the
message, saving some space.

Remove 4D informations: when set to Yes, Pip* will
eliminate all 4th dimension informations from seen-bies
and paths; you must enable it ONLY if you're a point of a
boss that uses an obsolete 3D mailer (like QM). See also
PIP ^SETELIM4D^ and ^RESETELIM4D^ commands.
*P
Remove ^^aREPLY kludge: when Yes, Pip Reply will not add a
^^aREPLY kludge to the message you'll generate. The ^^aREPLY
kludge essentially is a quote of the MSGID of the message
you're replying to. It was originally designed to be used
by a ^LINK^ utility, but since no known program really
utilize it, you may set it to Y and save some space on
disk and time in transmissions.

Remove domain from MSGIDs: if No, Pip* will generate
5-dimensional MSGIDs (including domain); otherwise,
shorter MSGIDs will be generated. You may leave it to Y,
and save space, time, and money if you're not linked to
inter-network conferences; see also the PIP ^SET5DMSGID^
command.
*P
Mailer used: it is the type of the program you use to
handle modem connections: Pip* has to know this
information to properly communicate with that program.
Possible values are B if your front-end mailer uses *.FLO
file attaches (like Binkley Term, MilqueToast and Lora),
or F if your mailer uses netmail *.MSG attaches, like
FrontDoor or D'Bridge). See also ^Setup\Directories^ and
PIP ^SETATTACHES^ commands.

Compress matrix: Set it to Y if you have answered a B to
the preceeding question (mailer used); otherwise, you may
specify a N to leave to the mailer the processing of
netmail or Y if you want Pip* doing it (Pip* is used to
compress outgoing netmail; D'Bridge and Front Door no).
See also PIP SETATTACHES.
*P
Add to tearline: this string will end your tearline, i.e.:
the line that will be placed at the end of your echomail
messages, just before the Origin (see ^Setup\Origins^);
Warning: some network policies require that the tearline
must contain only the names of the programs you used to
generate the message. See PIP ^ADDTEAR^.

Registration key: if you are registered, place here your
registration key, or use the PIP ^BOOST^ command.
Important: if you use the setup to insert the key, you'll
have to leave and reenter Pip* to make it effective.
See also: ^What About Registering?^
*P
Automatically create areas: if this parameter is set to Y,
when Pip* will found a message in an unknown echomail area,
that area will be created inthe first free area; otherwise,
it will be placed in the #BAD area; if the #BAD area does
not esxist, the message will be lost.
This option is enabled to registered users only.

Route crash mail via boss: when you send a crash mail 
message to a point of another BBS, usually it has to be
routed via its bossnode (you cannot call a point, since a 
point usually hasn't a modem-dedicate phone line), and
this field has to be left at Y. Set it to N if you want
crash messages to be placed in your outbound area 
separated from boss and points. Notice: this option 
hasn't any effect when running in a FD environment, since
Pip* leaves to FD all routing work.
*P
Flag (if possible) messages as sent during IMPORT: usually,
when you ^IMPORT^ messages, they're not flagged as sent;
when you issue an ^EXPORT^ command, all messages are 
flagged as sent, even if they're not actually exported
because the only friend you must export messages to is the
friend that sent you messages. This means that Pip* spends
a lot of time in modifying headers. By setting this option
to Y, Pip* will control, while importing messages, if they
come from the only friend in the list; if so, Pip* will
flag messages as sent, saving a lot of time during Export.
This option is useful for point installations, less useful
but not dangerous for BBSes and should be disabled only if
you plan to modify friend list and/or areas definitions 
between IMPORT and EXPORT (strange thing, but there is no
limit to things an user can think at), or if there are
manifested incompatibilities between PipBase and one of
your echomail feeders.
*E
*B 502,Setup\Directories
Setup\Directories

With this dialog box you'll may configure all directories
Pip* wil use.

Pip message base directory: where your messages will be
placed. Changing it is equivalent to issuing a PIP
^SETPIPDIR^ command: it will *NOT* move message base
files: you'll have to copy them manually in the new
directory.

Inbound directory: where your front end will place
incoming mail files (see PIP ^SETINBOUND^).

Outbound directory: where Pip* wil place outgoing mail
bundles (see PIP ^SETOUTBOUND^).
*P
Packer directory: where Pip* will search for packing
programs (like PkZip, PkUnZip, Arj, etc...). Leaving it
blank, Pip* will search all directories in PATH.

Temporary directory: Pip* will store here temporary files
(see PIP ^SETPIPDIR^).

Netmail file attaches: this directory is used only with
Front Door and D'Bridge front ends, to store fileattach
messages. Please refer to your mailer documentation.

Default packer (and parameters): see PIP ^SETPACKER^

Jolly unpacker (and parameters): see PIP ^SETUNPACKER^
*E
*B 503,Setup\Message Areas
Setup\Message Areas

With this option you'll may set all messages areas.

Use PgUp and PgDn to select the area you want to define
(or change); press Esc to leave area editing.

The area number (area#) is assigned by the system.

The area description is a description of the contents of
messages that will be contained in the area.

The area tag is an unique area identifier, used for mail
exchange. It is a name for echomail areas, the reserved
keyword #NETMAIL for netmail area, the reserved word #BAD
for an area where you want Pip* placing bad messages, or
#LOCAL for local (i.e.: not exchanged with other systes)
areas.
*P
Maximum messages and days: these values are used by the
^Mail\Purge^ or the PIP ^PURGE^ (see) commands and
they're the maximum number of messages the area will
contain after a purging.

Notes can be everything you want, but inserting in this
field some particular switches may be useful to activate
some oter programs. (i.e.: inserting a SV:filename.ext,
the filename.ext will be automatically copied in the file
window when you'll export a message on a file with PIP
^REPLY^).

Origin mode: for echomail areas, Pip reply may select
origins in three ways:
- Fixed (place the letter F in the "Origin mode" field
  and an origin number in the "Current origin" field):
  Pip* will always use the origin so defined.
*P
- Random (place the letter R in the origin mode field and
  two origin numbers in "from origin#" and "to origin#"
  fields): Pip* will randomly select an origin between
  the values.
- Cyclic (place the C letter in the mode field, an
  interval in "from#" and "to#" fields and a starting
  origin in the "Current origin" field): Pip* will cycle
  over all origins in the defined set.

Kill received messages: when set to Y, a ^PURGE^ command
will delete also all messages falgged as received. Leave
it to N unless for private areas.

Use aka#: when you have more than an address, set here
the index of the address you want to be placed in the
origin line.
*P
Export to friend list: only for echomail areas, this is a
list of friends you want to export the area to (see also
PIP ^SETEXPORT^ and ^RESETEXPORT^ commands).

An area is considered as deleted when you leave blank its
description and its tag.

If you added an area, a PIP ^PACK^ is performed when 
you'll exit from setup, to add new files.
You may also use PIP ^CREATE^ to create areas and then 
the setup to modify them.

If you deleted an area, this setup prompts for deletion of
messagebase files containing messages. Answer Yes if you 
want to clear the message base, or No if you want to keep
them in "ghost" files called M???xxxx.PIP (where xxxx is
the area number, in hexadecimal)
*E
*B 504,Setup\Origins
Setup\Origins

With this option you may change all your echomail origin
texts.

Origins are diplayed one at time; you may modify the
displayed origin or go to another origin with PgUp and PgDn
keys.

When you've finished, press Ctrl-Enter.

See also PIP ^SETORIGIN^, ^PICKORIGIN^, ^CREATE^ and
^Setup\Message Areas^
*E
*B 505,Setup\Network Addresses
Setup\Network Addresses

This option will open a window with all ten network
addresses you may define.

You'll be able to modify all addresses, and also the
fakenet numeber, but you should always define address#0
(your main address).

Use ctrl-Enter to terminate editing.

See also: PIP ^SETNODE^ and ^SETFAKE^
*E
*B 506,Setup\Friends
Setup\Friends

When you export mail to other systems, you'll have to
define them as "friends".

You must define a friend list, and refer to the friend
nodes with the number they have in this list. They're
numbered from 0.

Select this option, a window will appear with the first
record of the list. Scroll friends with PgUp and PgDn,
and leave the dialog box with Esc.

The friend number is assigned by the system. If you're a
point, place your boss as friend #0 (if your're a point,
place your hub at the first place): this will speed up
some operations.
*P
Address: it is an ordinary, 4-dimensions,
fidonet-compatible address, the address of your friend.

Packer: the program that you want to use to compress mail
for your friend.
With parameters: the parameters you must add to the
command line to add a file to an archive.

Areafix level: the level of the friend: it will be
matched with the area level when an areafix request will
arrive.

Areafix password: the password your friend has to use
when sending an areafix request (see also PIP ^AREAFIX^).
*P
Packet password: this password will be placed in the
header of all outgoing packets. Some software uses it for
security controls. If your friend uses Wmail, set it to
the same password you've for Areafix.

Active: usually it is Y; set it to N only if you want to
temporarily suspend mail exchange with that friend node,
but you don't want to loose all other settings.

Deleted: setting it to Y, the friend will be deleted when
you'll close the window. Be sure to set it to N when you
insert a new friend in place of an unexisting one!

Hold: set it to Y if you never want to call this friend.

Crash: set it to Y if you always want to use crash mail
with that friend (i.e.: when a mail packet is generated,
always call immediately the friend).
*P
See also: PIP ^SETFRIEND^ and ^LISTFRIENDS^
*E
*B 507,Setup\Routing
Setup\Routing

This command allows you to change the routing of netmail
messages.

What is the routing? "Routing" means that all your netmail
messages will be packed togheter and sent via an unique
node (a "Hub" or a "Host").

If you're a point, do not set any particular route: all
your messages will be sent through your boss node.

If you're a BBS, you may set a serie of routing rules:
when Pip* will try to pack a message, it will follow the
most specific rule that apply to that message.
*P
Every route rule is a record composed by the following
fields:

- Route mode
- Address
- Friend#

- Route mode: this field defines the specificity of the
  routing rule:
A: all messages will be routed following this rule;
Z: all messages for the zone specified in the address
   field will be routed via the specified friend;
R: all messages for the region ... bla, bla bla
N: all messages for the net ...
H: all messages for the hub ...
D: all messages foro the node ...
*P
P: all messages for the point ...
  If you place an E in nthis field, the contents will be
  delelted from the routing file when you'll exit this
  dialog box (by pressing Esc)

- Address is the address of the node or of the group of
  nodes for which you want to redirect messages. An entire
  zone is specified as zone:0/0.0; an entire net or region
  is specified as zone:net/0.0; a particular node (with
  all its points) or a hub is set as zone:net/node.0.

- Friend# is the number (in the friend list) of the friend
  BBS you want to route the message thru.

See also command-line options ^ADDROUTE^, ^LISTROUTE^ and
^DELROUTE^.
*E
*B 508,Setup\UUCP Gateway
Setup\UUCP Gateway

This setup option controls the automatic use of a UUCP
gateway between your fidonet-compatible network and
internet.

See also: PIP ^SETUUCP^
*E
*B 509,Setup\Users
Setup\Users

This option will display a window where all eight Pip*
users are listed.

You'll may modify them by selecting with cursor keys or
with the mouse the user you want to change and by typing
the new value.

Press Enter until the end of the form or press Ctrl-Enter
to stop editing.

See also: PIP ^SETUSER^ and ^LISTUSERS^ commands.
*E
*B 510,Setup\Robots
Setup\Robots

This setup options controls the Ghost Writer (see PIP
^GHOST^ and ^RR^ commands) and other robots you may install
with the PipBase Robot Engine.

The Ghostwriter's name is the name the Ghost Writer will
use in answering your messages.

The Return Receipt file is the name of the file the
Ghostwriter will send. If the file name is absent (i.e.:
blank), a default message will be generated.
*P
If you answer Y (yes) to "Kill received messages", all
Robots made with the PipBase Robot Engine will kill
processed messages. If you answer N, processed messages
will be simply flagged as "Received".

If you answer Y to "Kill robot answers", all answers
generated by the robots will be flagged as Kill/Sent (see
PIP ^POST^).

See also: PIP ^SETGHOST^, ^SETROBOT^ and ^SETRR^.
*E
*B 511,Setup\Log File
Setup\Log File

The log file is a text file where Pip* records all what is
happening.

With this option, you may alter the file name, the "log
level" (a number between 0 and 3; a higher level means that
you want more informations: the log file will be more
complete but longer), and the log style (B for a Binkley-
Term-like log or F for a Front-Door-like log).

See also PIP ^SET^, ^SETLOGFILE^, ^SETLOGTYPE^ and
^SETLOGLEVEL^.
*E
*B 512,Setup\Editor Preferences
Setup\Editor Preferences

This dialog box allows you to setup all parametes needed
to write messages with the interactive message editor.

Editor name: this is the commnd you usually issue
(followed by the name of the file to edit) to invoke your
favourite text editor (like SLED, EDIT, NEDIT, ME2, or
even EDLIN). If you leave this field blank, Pip internal
editor will be used (it is not so good as many other
editors). This editor will be used for text editing.

Swap when running external editor: set this field to Y if
you editor requires a lot of memory (e.g.: ME2 or
Microsoft Word), to N otherwise. If set to Y, Pip* will
swap its code to disk or EMS, slowing down operations but
freeing all low memory. If you use the internal text
editor, this field is ignored.
*P
Quote preamble: this string will be placed at the top of
the quoted text (a message is quoted when you copy it in
order to reply to it). You may insert a %n (where n is a
number from 0 to 9) to insert in the text some datas,
those listed in the dialog box.

Left margin: this string will be placed at the left
margin of the quoted text. Notice that most message
editors require that it contains the initials of the
message sender and that it ends with a '>' in order to
properly recognize quoted text.

Quote kludges: set it to Y if you want kludges (hidden
lines) quoted with the text, to N otherwise.
*P
Message template: this line of text will be placed at the
start of all new messages (not replies) that you'll
write. You may use a %9 to indicate a newline.

Signature: this string will be added to every message
you'll write. A %9 will indicate a newline.

Primary and secondary userlist files: theese fields are
the complete paths of two ^userlist^s (see).

Alias list: this is the complete path and file name of
the ^alias list^ file (see).

Default netmail flags: set to Y the flags that you want
always to be set when entering a new messages in a
#NETMAIL area (see the ^Flags^ screen in Pip Reply).
*P
Extended headers when forwarding a message: usually, when
you forward a message, it is preceeded by a little header,
to signal who was the original addressee. If you set this
field to Y, this header will contain much more
informations (address, date, original subject...),
resulting in longer messages.
*E
*B 513,Setup\Quotes
Setup\Quotes
This window allows you to define personalized quote
templates for each of your friends.

When you reply to a message, the message text will be
quoted in the answer, preceeded by a preamble and with
some string in the left margin (see also
^Setup\Editor Preferences^).

With Pip* you may chhose a different way to quote
messages for each of your telematic friends.

This is a list of up to 200 personalized quotes; this
list will be browsed every time you'll quote a message:
if Pip* will not find the sender in this list, the
default quote string will be used.
*P
Use PgUp and PgDn to browse the list; Esc to abandon it.

The first field is the complete name of you friend,
properly capitalized.

The quote preamble is the string that will be placed at
the top of the quoted message. You may use %0 .. %9 to
insert some variable datas in it.

The left margin will be repeated at the left of every
quoted line. a %0> is usually accepted from most editors
(%0> will place sender's initials followed by a >).

Areas is a list of up to 10 message area numbers: if this
list is present, the personalized quote will be used only
in listed areas.
*P
To delete a personalized quote, simply delete the first 
field and then exit.
*E
*B 514,Setup\Colors
Setup\Colors
This menu allows you to configure all Pip* colors.

Selecting the Setup\Colors option, a menu will appear with
the list of all the items you can change color to.

Select an item from this menu and a color selection window
will appear: select the color you want for the item and
press Enter (or click mouse button).
*E
*B 515,Setup\Viewer
Setup\Viewer

This option displays a configuration dialog box where you
may set all options related to the message displaying:

External Viewer: this is the command that will be ran when
you'll press [V] from the ^Pip Reply main screen^ to view
messages with alternate viewers.

Use Viewer: this field lets you specify when to use the
external viewer defined in the previous field: set it to N
if you want to never use it, Y if you want to use it only
when you press [V] or A if you want to see all messages
through the viewer (it's slow).

See also: ^External Viewer^
*P
Screen width and height: the size of your screen; usually,
you'll have to maintain the width at 80 columns and the
height at 25 (CGA), 43 (EGA) or 50 (VGA) lines. This
setting may be overriden by the ^/25^ switch (see).

View Kludges: when Y you'll see also the hidden text in
messages.

Use Sound: self-explanatory: if N, Pip Reply will be mute.

User: this is the number of the user (see PIP ^LISTUSERS^)
that acceeds th message editor; it's used to maintain the
proper lastread pointers (see PIP ^SETLASTREAD^) and is
overriden by the PIP ^REPLY^ /U=... switch (see); set it to
-1 if you don't want to maintain lastread pointers.
*P
Initial Area: the number of the area you want to
automatically enter when running the message editor Pip
^REPLY^; set it to -1 if you want Pip asking you the area
every time you'll run it. It may be overriden by the /M=
switch on the command line.

Direct Video Access: set it to Y for the maximum
performance; revert to N to use BIOS access (much slower!)
if the direct access causes problems with your (obsolete)
video adapter.

Park Mouse: a number form 0 to 4 codes where the mouse
cursor will be placed when PIP* starts; this is because
some users don't like a mouse cursor always at the center
of the screen if they don't use it.
*P
Automatic Area Change: when you've finished to read
messages in a message area and you press right cursor or
Enter to read another message, Pip* can go directly to the
change area screen (set this parameter to A), go to that
screen after asking for confirm (set this parameter to Y),
or stay in that area (set it to N).

Export: these options controls the aspect of the messages
exported with the [X] key form PIP ^REPLY^ main screen, but
only in registered version: separation line will add (if
set to Y) a line of minus between a message and another;
export kludges (if Y) will export also the hidden text and
status will export (if Y) also message flags.

Display clock: if set to Y, a little digital clock will be
always kept in the top-right corner of the screen. If you
aren't registered, you cannot disable it.
*P
Mark areas with unread messages in area list: if set to Y,
when you'll enter an area selection list, areas containing
unread messages (i.e.: areas having the lastread bookmark
before the last message) will be marked with an asterisk.
This will considerably slow down operations; to be faster,
forget marks and set this option to N. (see also
^Pip Reply area selection^).

Suppress BELs from beeping messages: you may create a 
beeping message by inserting a CTRL-G (BEL) character in
message text; usually, a message reader will beep when
displaying your messages. If you set this option to Y,
Pip* will not ring, but it will display a smily face
instead.
*P
Ask for a key after executing commands from menu: if you
set this option to Y, Pip* will ask you for pressing any 
key after every execution of an option from the
^Pip Mail Menu^ (except for Editor option). If you set it
to N, you'll be prompted only after a ^Mail\Statistics^
option (Pip* MUST pause, to show the results of your
query).

*E
*B 550,External Viewer
The external viewer

To see messages, you may use an alternate text viewer,
useful when messages contain TeX commands, or music, or
bitmaps (Warning: in most networks these things are not
accepted by policy).

Pip Reply can automatically save the message you're
reading in a plain ASCII text file and run a program
called "external viewer".

You may set everything as a viewer. Pip* will run the
command you defined in ^Setup\Viewer^, adding to it only
the name of the file containing the text (usually
MsgTmp.Lst).
*P
How is that text saved?

The MsgTmp.Lst file has the following format:

Area#xxxx (tagname,description)
Msg #xxxx
Date:dd Mon yyyy hh:mm:ss
From:name (address)
To  :name (address)
Subj:xxxx
Stat:xxxx yy
<message text>

The message text is saved as-is, without word-wrapping and
with all kludges (kludge lines area preceeded by a
Ctrl-A); xxxx and yy in the message status (Stat:) line
are two hexadecimal numbers: the FSC-0001 message
attribute flags and an internal Pip* status flag (bit
*P
0=deleted; bit 4=locked; other flags are duplicated from
the attributes).

All other numbers are decimals.

*E
*B 551,userlist
What's a userlist?

When you write a netmail message, you'll have to insert
the address of the people you're writing to. Addresses
are rather ugly to remember, and so, why don't store them
in a file, and let the editor retrieve them from the
name?
A userlist is one of such files.

PipReply uses the standard FidoUser.Lst format for the
user list, with some extensions.
A fidouser.Lst is a sequence of lines, exactly 60
characters long and terminated with a CR/LF (so that you
may access it randomly, with fixed-length records) and of
the format:
Last_name, First_name                                address
*P
(address is not necessarily left-justified: it can be
followed by spaces to fill all 60 characters).

Rows in the list have to be alphabetically ordered.

A List like this is automatically generated by a 
^nodelist/pointlist compiler^ from the St.Louis Nodelist 
(i.e.: the distribution format of the fidonet nodelist), 
or from a a pointlist (distributed like the nodelist in
some networks); you may also write your own list
using any text editor or use ^BuildList^

PipReply accepts these extensions:
a) address can be a complete four-dimensional address.
b) address can be also an internet address.

Let's see an example:
*P
Aalsburg, Hans Van                                   285/508
Abelmann, Guus                                       286/304
Aerts, Robert                                        280/308
Amosso, Gian                                         334/305

is a standard fidouser.lst file generated by Parselist.

Bernardotti, Flavio                flavio@montal.sublink.org
Calorio, Matteo                                  2:334/306.3
Dieni, Cesare                        cesare@wolf.sublink.org
Marchetti, Federico             marchett@pianeta.di.unito.it

is also accepted. When you write to a friend via
internet, the UUCP gateway is automatically used
(remember to set PIPBASE SETUUCP).
*P
PipReply can use two userlist: if it does not find a name
in the first list, it will browse the second before
asking you for the address. It's useful to assign the
first userlist to the standard userlist distributed (or
generated) with the nodelist, and inserting in the
secondary list unlisted points and internet addresses.

For one-word names: short names, nicknames, and so on,
you've to put them in the userlist preceeded by a comma:

, Ago                                            2:332/210.1
, Areafix                                          2:334/306
because they're considered as last names.
Since the ASCII code for the comma is less than any
letter, you'll have to place them at the top of the
userlist.
*E
*B 552,alias list
What's an alias list?

An alias is a nickname that you may use instead of the
ful name when writing messages.
If you define an alias list, when you insert a new
message you can use an alias expansion: write only a
(short) nickname, press F9 and the complete name will
appear in the name field.

An alias list file is a text file. Each line is composed
with the nick name, a comma, and the complete name. E.g.:

Hal,Alberto Ferrari
Mac,Maurizio Macagno
Fab,Fabrizio Croce

Notice: tis option can be used by registered users only.
*E
*B 553,nodelist/pointlist compiler
Accreditated nodelist compilers are:

- ParseList (the old good ParseList, the first compiler
  cannot be forgotten)

- FastList (a quick, italian replacement for ParseList,
  made by Alberto Pasquale, 2:332/504.0@fidonet.org)

- MakeList (especially made for Pip* by Paolo Rosa, 
  2:334/400.4@fidonet.org)

MakeList compiles also the pointlist; parseList and
FastList generate also the BBS nodelist required by most
front ends (like Binkley Term).
*E
*B 554,BuildList
Buildlist is a program of mine.

It creates an userlist extracting addresses from a message
area.

It can be found as BLDLST*.* on support BBSes
*E
*B 600,Pip Menu Help
This is the main menu screen.

Select a topic with cursor keys and Enter (or by clicking 
with mouse):

^Help on help^
^Interactive use^
^Pip General Menu^
^Pip Mail Menu^
^Pip Setup Menu^
^PipBase Info^
^PipBase Help^
*E
